Exchange 2013 CAS receive connector gives "451 4.7.0 Temporary server error. Please try again later. PRX1"

Hi,

We have an very strange issue with Exchange 2013 (CU8, issue was the same with CU7) and receive connector on CAS. We have 1 CAS server,1 Edge and 2 Mailbox servers. This started to happen when 2010 was uninstalles/removed. Everything worked before 2010 was removed. 

We have a seperate Receive connector for mail relay from scanner/software etc. If we try to send to external addresses (user@external.com) we got this response:

"
451 4.7.0 Temporary server error. Please try again later. PRX1"

If we send with internal address (user@internal.com) its works. Anonymous access is configured. The strange thing is that when we test and send a test-message with both internal and external address (user@internal.com; user@external.com), both is delivered OK. 

Used this commands to test:
This command works:
Send-MailMessage -From test@internal.com -To user@external.com,user@internal.com -Subject TestMail -SmtpServer serverip

This command gives errorcode:
Send-MailMessage -From test@internal.com -To user@external.com -Subject TestMail -SmtpServer serverip

Send-MailMessage : Error in processing. The server response was: 4.7.0 Temporary server error. Please try again later.
PRX1
At line:1 char:1
+ Send-MailMessage -From test@internal.com -To user@external.com -Subject Te ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.Mail.SmtpClient:SmtpClient) [Send-MailMessage], SmtpExcept
   ion
    + FullyQualifiedErrorId : SmtpException,Microsoft.PowerShell.Commands.SendMailMessage

We have created an case with Microsoft, but the response from MS is very bad/nothing.

Anyone that have seen this behavior?

Thanks

Lars Erik

March 25th, 2015 10:59am

Hi Lars,

Thank you for your question.

we could check if the Exchange 2010 have removed completely by the following steps:

  1.        Run ADSIEDIT.msc in RUN,
  2.        Navigate to Configuration [<domainController>.contoso.com]> CN=Configuration,DC=contoso,DC=com> CN=Services> CN=Microsoft Exchange> CN=<OrganizationName> CN=Administrative Group> CN=Exchange Administrative Group>CN=Server
  3.        We could check if mailbox server is existed in this container, we could remove it.

We could disable A/V to check if the issue persist.

If there are any questions regarding this issue, please be free to let me know. 

Best Regard,

Jim

Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 3:07am

Thanks for the the reply.
Non of the old exchange servers is present in the Container. Only the 2013 servers. A/V is already disabled.

Best Regard,

Lars Erik

March 26th, 2015 3:41am

Some more info. 

I looked into the logfiles on Exchnage (V15\TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive) and I find this:

"No destinations could be obtained to proxy to" when using only external address.

When using both adresses (internal and external):

"Proxy destination(s) obtained from OnProxyInboundMessage event"

Lars Erik

Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 8:31am

May be i have a solution for you.
May 12th, 2015 11:54pm

Morning,

Did you ever get a solution to this problem?

Having the exact same problem and I cannot find any resolutions!

Thanks 

Free Windows Admin Tool Kit Click here and download it now
July 7th, 2015 2:12am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics